Description

Fixes a Babel transform-time error that caused @react-native/babel-plugin-codegen to throw "Could not find component config for native component" during Metro bundling in Expo projects. The error occurred because Metro was resolving to the compiled lib/module/ files (produced by react-native-builder-bob), which have TypeScript type annotations stripped — but the codegen Babel plugin requires those annotations to generate inline view configs for Fabric components. Adding a react-native condition to the exports map causes Metro to resolve to the TypeScript source files instead, where the NativeProps interfaces are intact.

Also adds react-native.config.js to declare the SDK's native dependency explicitly, including BoltGooglePayButtonComponentDescriptor in the Android componentDescriptors array to ensure correct Fabric
component registration via autolinking.

Testing

• Created a fresh Expo project, installed the SDK as a local tarball, added imports of ApplePay and GoogleWallet from @boltpay/react-native/payments, and ran expo run:ios and expo run:android — both
  platforms bundled and launched without the "Could not find component config" error.
• Confirm BoltProvider, ApplePay, and GoogleWallet imports resolve correctly in a consumer project.
• All 115 existing unit tests pass.

Security Review

• I have considered and reviewed security implications of this PR and included the summary below.

Security Impact Summary

No security-sensitive changes. This PR only modifies module resolution configuration (package.json exports map) and autolinking configuration (react-native.config.js). It does not touch authentication, payment flows, user data handling, or external integrations.